Massive multiple-input-multiple-output (mimo) uplink enhancement in split radio access network (ran) deployments

ABSTRACT

Aspects of the subject disclosure may include, for example, a system comprising a distributed unit (DU) configured to generate sounding reference signal (SRS)-based beams, and a remote unit (RU) communicatively coupled with the DU over a fronthaul, wherein the RU is configured to generate demodulation reference signal (DMRS)-based beams and perform digital beamforming for an uplink using the DMRS-based beams in combination with the SRS-based beams. Other embodiments are disclosed.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional Application Ser. No. 63/333,890, filed on Apr. 22, 2022. The contents of the foregoing are hereby incorporated by reference into this application as if set forth herein in full.

FIELD OF THE DISCLOSURE

The subject disclosure relates to combined beamforming (BF), channel information transfer allocation, and reference signal compression for massive multiple-input-multiple-output (MIMO) uplink enhancement in wireless radio access networks (RANs) deployed with a fronthaul split or any other lower, physical layer split.

BACKGROUND

A split configuration, such as an open-RAN (O-RAN)-specified fronthaul split (or any other lower, physical layer split), enables deployment of communication units across large geographic areas, where processing for those units is implemented in a centralized (e.g., cloud-based) system. Split fronthaul, in particular, allows network operators to deploy cheap and lightweight radio units (RUs) or open-RUs (O-RUs) on cellular towers that are connected to baseband processing systems (i.e., distributed units (DUs) or open-DUs (O-DUs)) via digital interface(s). The interface and messaging between a DU and an RU are openly specified in standards bodies, such as O-RAN. A major requirement for a fronthaul interface is the ability to exchange radio data via low throughput messaging while maintaining adequate communication performance. Extensive efforts were made to define the O-RAN split fronthaul message exchange format to ensure that communication performance is maximized at the lowest possible throughput.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1A is a block diagram illustrating an exemplary, non-limiting embodiment of a communications network in accordance with various aspects described herein.

FIG. 1B is a block diagram illustrating an example, non-limiting embodiment of a system functioning within, or operatively overlaid upon, the communications network of FIG. 1A in accordance with various aspects described herein.

FIG. 2A is a timing diagram illustrating a process for beamforming from a sounding reference signal and a delay in applying the beamforming to a physical resource shared channel uplink transmission.

FIG. 2B is a block diagram illustrating an example, non-limiting embodiment of a system functioning within, or operatively overlaid upon, the communications network of FIG. 1A and/or the system of FIG. 1B in accordance with various aspects described herein.

FIG. 2C illustrates various example uses of the system of FIG. 2B in accordance with various aspects described herein.

FIG. 2D is a block diagram illustrating an example, non-limiting embodiment of a system functioning within, or operatively overlaid upon, the communications network of FIG. 1A and/or the system of FIG. 1B in accordance with various aspects described herein.

FIG. 2E depicts an illustrative embodiment of a method in accordance with various aspects described herein.

FIG. 3 is a block diagram illustrating an example, non-limiting embodiment of a virtualized communications network in accordance with various aspects described herein.

FIG. 4 is a block diagram of an example, non-limiting embodiment of a computing environment in accordance with various aspects described herein.

FIG. 5 is a block diagram of an example, non-limiting embodiment of a mobile network platform in accordance with various aspects described herein.

FIG. 6 is a block diagram of an example, non-limiting embodiment of a communication device in accordance with various aspects described herein.

DETAILED DESCRIPTION

Careful consideration needs to be made in the design and implementation of communication exchanges (e.g., how data is transferred, the type of data that is transferred, how often the data is transferred, and so on) between a DU and an RU in a split fronthaul configuration to ensure that the fronthaul interface is not overburdened. This is especially so in massive MIMO deployments where RUs may have numerous (e.g., 64, 128, etc.) antennas, and data for numerous user equipment (UEs) needs to be extracted from uplink signals (or “chains”) for processing at a centralized baseband processor.

The existing fronthaul split, which is well defined in O-RAN, distributes uplink processing work between the O-RU and the O-DU at the beamforming stage. In particular, the RU performs beamforming of an uplink signal by multiplying a received signal with a beamforming matrix. Each column of the beamforming matrix may be referred to as a “beam,” and the output of beamforming is a collection of signal streams that are sent over the fronthaul interface to the DU. In a typical fronthaul split configuration, beams are designed by the DU based on sounding reference signal (SRS) processing (i.e., channel estimates based on SRS data provided by UEs) and are communicated to the RU for use in a digital beamformer to process uplink signals. However, because the beams are generally designed by the DU prior to signal reception by the RU, the issue of beam aging arises. Specifically, some amount of time (e.g., milliseconds) would have passed between initial receipt of SRS data from a given UE and the eventual updating of the digital beamformer, and during this time, the channel between the UE and the RU may have changed. This renders the beams outdated and communication performance may thereby suffer.

The subject disclosure describes, among other things, illustrative embodiments of combined beamforming in which an RU is configured to generate beam(s) using (the latest) received uplink signal information (e.g., demodulation reference signal (DMRS) data), and selectively combine these beam(s) with beam(s) generated by a DU (e.g., based on SRS data) for uplink beamforming. In exemplary embodiments, combination of the differently generated beams may be in the form of simple concatenation, where the digital beamformer's multiplication matrix may be updated with the various beams. In a simple, example scenario, the matrix may include a first column for a first beam generated by the RU using DMRS data and a second column for a second beam generated by the DU using SRS data, and the DU may (request and) obtain two streams from the RU—i.e., one generated using the DMRS-based beam and another generated using the SRS-based beam—and extract and use data from both streams so as to harvest the benefits of both DMRS (which might be a bit noisy, but is the most up-to-date) and SRS (which might be slightly dated, but is intensively processed by the DU to reduce noise/eliminate interference).

In various embodiments, and described in more detail herein, an artificial intelligence (AI)/machine learning (ML) compute system residing in a network (e.g., a RAN intelligent controller (RIC) or the like) may learn and adjust allocation of beam design responsibilities between a DU and an RU in accordance with performance indicator(s). Various factors can be used in the allocation decision-making, including user priority, user reliability/latency requirements and/or service level agreements, user channel conditions, user mobility, content type, fronthaul load, DU load, RU load, resource usage patterns, instantaneous user loading, and so on to optimize or improve load balancing in the fronthaul.

Exemplary embodiments described herein leverage the available compute resources of a DU and the presence of the most up-to-date uplink signal information in an RU to dynamically optimize or improve beamforming in uplink massive MIMO systems. The ability to effect combined beamforming is especially useful in distributed deployments of MIMO cellular base stations. Further, AI/ML compute systems in a radio network can control the optimization with minimal to no need for analysis or classification of deployment types and with minimal to no need for manual intervention.

One or more aspects of the subject disclosure include a system, comprising a distributed unit (DU) configured to generate sounding reference signal (SRS)-based beams, and a remote unit (RU) communicatively coupled with the DU over a fronthaul, wherein the RU is configured to generate demodulation reference signal (DMRS)-based beams and perform digital beamforming for an uplink using the DMRS-based beams in combination with the SRS-based beams.

One or more aspects of the subject disclosure include a method. The method can comprise generating first beam weights by a first processor of a distributed unit (DU) in a network. Further, the method can include transmitting, by the first processor, the first beam weights to a remote unit (RU) of the network, wherein the DU and the RU are communicatively coupled to one another via a split fronthaul. Further, the method can include generating second beam weights by a second processor of the RU. Further, the method can include performing digital beamforming for an uplink of the network based on the first beam weights and the second beam weights.

One or more aspects of the subject disclosure include a device, comprising a processing system including a processor and a memory that stores executable instructions that, when executed by the processing system, facilitate performance of operations. The operations can include obtaining sounding reference signal (SRS) data from a user equipment (UE) in an uplink. Further, the operations can include providing the SRS data to a centralized control unit over a fronthaul shared by the device and the centralized control unit. Further, the operations can include receiving a command from the centralized control unit to utilize demodulation reference signal (DMRS)-based beams in digital beamforming for the UE. Further, the operations can include generating one or more DMRS-based beams based on the command. Further, the operations can include performing the digital beamforming using the one or more DMRS-based beams.

Other embodiments are described in the subject disclosure.

Referring now to FIG. 1A, a block diagram is shown illustrating an example, non-limiting embodiment of a system 100 in accordance with various aspects described herein. For example, system 100 can facilitate, in whole or in part, combined beamforming, channel information transfer allocation, and/or reference signal compression for massive MIMO uplink enhancement in wireless RANs deployed with a fronthaul split or any other lower, physical layer split. In particular, a communications network 125 is presented for providing broadband access 110 to a plurality of data terminals 114 via access terminal 112, wireless access 120 to a plurality of mobile devices 124 and vehicle 126 via base station or access point 122, voice access 130 to a plurality of telephony devices 134, via switching device 132 and/or media access 140 to a plurality of audio/video display devices 144 via media terminal 142. In addition, communications network 125 is coupled to one or more content sources 175 of audio, video, graphics, text and/or other media. While broadband access 110, wireless access 120, voice access 130 and media access 140 are shown separately, one or more of these forms of access can be combined to provide multiple access services to a single client device (e.g., mobile devices 124 can receive media content via media terminal 142, data terminal 114 can be provided voice access via switching device 132, and so on).

The communications network 125 includes a plurality of network elements (NE) 150, 152, 154, 156, etc. for facilitating the broadband access 110, wireless access 120, voice access 130, media access 140 and/or the distribution of content from content sources 175. The communications network 125 can include a circuit switched or packet switched network, a voice over Internet protocol (VoIP) network, Internet protocol (IP) network, a cable network, a passive or active optical network, a 4G, 5G, or higher generation wireless access network, WIMAX network, UltraWideband network, personal area network or other wireless access network, a broadcast satellite network and/or another communications network.

In various embodiments, the access terminal 112 can include a digital subscriber line access multiplexer (DSLAM), cable modem termination system (CMTS), optical line terminal (OLT) and/or other access terminal. The data terminals 114 can include personal computers, laptop computers, netbook computers, tablets or other computing devices along with digital subscriber line (DSL) modems, data over coax service interface specification (DOCSIS) modems or other cable modems, a wireless modem such as a 4G, 5G, or higher generation modem, an optical modem and/or other access devices.

In various embodiments, the base station or access point 122 can include a 4G, 5G, or higher generation base station, an access point that operates via an 802.11 standard such as 802.11n, 802.11ac or other wireless access terminal. The mobile devices 124 can include mobile phones, e-readers, tablets, phablets, wireless modems, and/or other mobile computing devices.

In various embodiments, the switching device 132 can include a private branch exchange or central office switch, a media services gateway, VoIP gateway or other gateway device and/or other switching device. The telephony devices 134 can include traditional telephones (with or without a terminal adapter), VoIP telephones and/or other telephony devices.

In various embodiments, the media terminal 142 can include a cable head-end or other TV head-end, a satellite receiver, gateway or other media terminal 142. The display devices 144 can include televisions with or without a set top box, personal computers and/or other display devices.

In various embodiments, the content sources 175 include broadcast television and radio sources, video on demand platforms and streaming video and audio services platforms, one or more content data networks, data servers, web servers and other content servers, and/or other sources of media.

In various embodiments, the communications network 125 can include wired, optical and/or wireless links and the network elements 150, 152, 154, 156, etc. can include service switching points, signal transfer points, service control points, network gateways, media distribution hubs, servers, firewalls, routers, edge devices, switches and other network nodes for routing and controlling communications traffic over wired, optical and wireless links as part of the Internet and other public networks as well as one or more private networks, for managing subscriber access, for billing and network management and for supporting other network functions.

FIG. 1B is a block diagram illustrating an example, non-limiting embodiment of a system 160 functioning within, or operatively overlaid upon, the communications network 100 of FIG. 1A in accordance with various aspects described herein. For example, system 160 can, in whole or in part, facilitate combined beamforming, channel information transfer allocation, and/or reference signal compression for massive MIMO uplink enhancement in wireless RANs deployed with a fronthaul split or any other lower, physical layer split. In some embodiments, the system 160 may correspond to or include one or more networks (e.g., a communications network, a data network, etc.).

As shown in FIG. 1B, the system 160 may include a RAN 162 a communicatively coupled to a core network 190. The core network 190 can include a 5G network, an evolved packet core (EPC) network, a higher generation network, or any combination thereof. In various embodiments, the RAN 162 a may be or may include a virtual RAN (vRAN) (e.g., in an O-RAN implementation) in which software is decoupled from hardware and implementation thereof is in accordance with principles of network function virtualization (NFV), where the control plane is separated from the data plane. The vRAN may include a centralized set of baseband units located remotely from antennas and remote radio units and may be configured to share signaling amongst cells.

As shown in FIG. 1B, the RAN 162 a may include a network service management platform 163 a and a RAN intelligent controller (RIC) 164 a. The RIC 164 a may include a RIC portion 164 a-1 implemented, or otherwise incorporated, in the network service management platform 163 a. The RIC 164 a may include a RIC portion 164 a-2 having a control or centralized unit (CU) 174 a (e.g., a base station CU, such as a gNodeB (gNB) CU or the like) that provides a CU applications layer 176 a as well as a CU control plane CU-CP and a CU user plane CU-UP (e.g., represented as CU-CP & CU-UP 178 a). In various embodiments, the RIC portion 164 a-1 may be configured to operate in non-real-time, and the RIC portion 164 a-2 may be configured to operate in near real-time. The particular functions performed by the RIC portions 164 a-1, 2 can vary based on various criteria, including implementing changing parameters or requirements for the network, and can also include redundancy and/or dynamic switching of functions (including functions described herein) between the RIC portions 164 a-1, 2.

As shown in FIG. 1B, the RAN 162 a may include distributed units (DUs) 166 a-1 through 166 a-L (L≥1) (hereinafter referred to collectively as “DUs 166 a,” and individually as “DU 166 a”). In various embodiments, the DUs 166 a may include baseband units (e.g., base station DUs, such as gNB DUs or the like) configured to perform signal processing, UE scheduling, and/or the like. In exemplary embodiments, each of one or more DUs 166 a may be implemented as a virtual DU (vDU). The RAN 162 a may also include remote radio heads or remote units (RUs) 168 a-1 through 168 a-M (M≥1) (hereinafter referred to collectively as “RUs 168 a,” and individually as “RU 168 a”). The RUs 168 a may communicatively couple (e.g., via an air interface) with user equipment (UEs) 170 a-1 through 170 a-N (N≥1) (hereinafter referred to collectively as “UEs 170 a,” and individually as “UE 170 a”). In various embodiments, the RUs 168 a may include remote radio units, antennas, and/or the like. In one or more embodiments, each of one or more RUs 168 a may include one or more antenna arrays (e.g., massive MIMO arrays).

As shown in FIG. 1B, the RUs 168 a, the DUs 166 a, and the CU 174 a may, by way of a fronthaul 181 a, a midhaul 182 a, and a backhaul 183 a, provide (e.g., controlled) connectivity between the core network 190 and the UEs 170 a. In one or more embodiments, the fronthaul 181 a, the midhaul 182 a, and/or the backhaul 183 a may conform to open standards, such as O-RAN standards or the like. In certain embodiments, a given DU 166 a may reside at a central location (away from cell towers) and may be communicatively coupled to multiple RUs (e.g., distributed across a geographic area) via a fronthaul 181 a (split fronthaul).

Although FIG. 1B illustrates the CU 174 a and the RIC portion 164 a-2 as being distinct from one another, in various embodiments, the CU 174 a may alternatively be incorporated in the RIC portion 164 a-2. In some embodiments, the RIC 164 a and the network service management platform 163 a may operate as part of one or more central control planes that oversee a geographic region that can include multiple (e.g., hundreds, thousands, etc.) of remote units, distributed units, centralized units, or any combination thereof.

In various embodiments, the system 160 may be functionally separated or segmented in accordance with one or more time-based zones or frames. For example, the network service management platform 163 a and/or the RIC portion 164 a-1 may be operative at or in non-real-time; the RIC portion 164 a-2 and/or the CU 174 a may be operative at or in near-real-time; and the DUs 166 a, the RUs 168 a, and/or the UEs 170 a may be operative at or in real-time. As the terms (and related terms) are used herein, real-time operations may occur over a span of fractions of a second up to a second (or the like), near-real-time operations may occur over the course of a few seconds (e.g., 1 to 5 seconds or the like), and non-real-time operations may occur over a time period that is greater than a few seconds (e.g., greater than 5 seconds or the like).

In various embodiments, the network service management platform 163 a may manage, or otherwise adapt, RIC behaviors and/or operations across one or more of the three time zones or timeframes described above (e.g., real-time, near-real-time, and non-real-time) on an individualized and/or collective basis. Such management or adaptation of RIC behaviors and/or operations may conform to one or more models or microservices (e.g., AI models or microservices) or network applications (e.g., rAPPs, xAPPs), as described herein. In turn, the RIC may establish and/or modify policies and/or behaviors of respective CUs, DUs, and RUs in accordance with the model(s) or micro service(s). In this regard, the network service management platform 163 a may indirectly influence the behaviors and/or operations of CUs, DUs, and/or RUs via one or more RICs.

In some embodiments, the communication channels and/or links between the RAN 162 a and the UEs 170 a may include wireless links. In various embodiments, some or all of the UEs 170 a may be mobile and may therefore enter and/or exit a service or coverage area associated with the RIC 164 a. In various embodiments, some of the UEs 170 a may include non-mobile or stationary devices. In some of these embodiments, the RAN 162 a may include one or more routers, gateways, modems, cables, wires, and/or the like, and the communication channels and/or links between the RAN 162 a and such UEs may include wired/wireline links, optical links, etc.

In various embodiments, a RIC (e.g., the RIC portions 164 a-1, 2 of the RIC 164 a) may store, execute, and/or deploy applications or microservices that are configured to control and manage a RAN (e.g., the RAN 162 a). In one or more embodiments, for example, the RIC portion 164 a-1 may store, execute, and/or deploy rApps, and the RIC portion 164 a-2 may store, execute, and/or deploy xApps (e.g., in or via an applications layer, such as the CU applications layer 176 a). The applications or microservices may relate to beam designing/forming responsibility allocation, scheduler capacity optimization, coverage optimization, capacity optimization (including, for example, via interference mitigation), user quality optimization (including, for example, for the uplink (UL) and/or the downlink (DL)), radio connection management, mobility management, quality-of-service (QoS) management, interference management, telemetry, network traffic control and/or management, device admissions (e.g., UE admissions control), and/or the like. In various embodiments, an application may include one or more models, such as AI (e.g., ML) models that, when executed in one or more containers, provide corresponding microservices. Deployment of an AI model in a RIC (or, more generally, a RAN) may involve, or include, for example, executing or instantiating the AI model in one or more containers in the RIC portion 164 a-1 and/or the applications layer of the RIC portion 164 a-2 (e.g., the CU applications layer 176 a), such that the AI model processes inputs (e.g., received from other microservices running on the RIC and/or from various components of the RAN, such as the CU-CP & CU-UP 178 a, the DUs 166 a, and/or the RUs 168 a) and provides outputs (e.g., to the other microservices and/or the various components of the RAN), in accordance with the AI model, to control the overall operation of the RAN.

It is to be appreciated and understood that the system 160 can include various quantities of cells (e.g., primary cells (Pcells) and/or secondary cells (Scells)), various quantities of network nodes in a cell, and/or various types of network nodes and/or cells (e.g., heterogeneous cells, etc.).

It is also to be appreciated and understood that the quantity and arrangement of systems, networks, platforms, controllers, controller portions, centralized units, applications layers, distributed units, remote units, fronthauls, midhauls, backhauls, and/or antenna arrays shown in FIG. 1B are provided as an example. In practice, there may be additional systems, networks, platforms, controllers, controller portions, centralized units, applications layers, distributed units, remote units, fronthauls, midhauls, backhauls, and/or antenna arrays than those shown in FIG. 1B. For example, the system 160 can include more or fewer systems, networks, platforms, controllers, controller portions, centralized units, applications layers, distributed units, remote units, fronthauls, midhauls, backhauls, and/or antenna arrays. Furthermore, two or more systems, networks, platforms, controllers, controller portions, centralized units, applications layers, distributed units, remote units, fronthauls, midhauls, backhauls, or antenna arrays shown in FIG. 1B may be implemented within a single system, network, platform, controller, controller portion, centralized unit, applications layer, distributed unit, remote unit, fronthaul, midhaul, backhaul, or antenna array shown in FIG. 1B or a single system, network, platform, controller, controller portion, centralized unit, applications layer, distributed unit, remote unit, fronthaul, midhaul, backhaul, or antenna array shown in FIG. 1B may be implemented as multiple, distributed systems, networks, platforms, controllers, controller portions, centralized units, applications layers, distributed units, remote units, fronthauls, midhauls, backhauls, or antenna arrays. Additionally, or alternatively, a set of systems, networks, platforms, controllers, controller portions, centralized units, applications layers, distributed units, remote units, fronthauls, midhauls, backhauls, and/or antenna arrays (e.g., one or more systems, networks, platforms, controllers, controller portions, centralized units, applications layers, distributed units, remote units, fronthauls, midhauls, backhauls, and/or antenna arrays) of the system 160 may perform one or more functions described as being performed by another set of systems, networks, platforms, controllers, controller portions, centralized units, applications layers, distributed units, remote units, fronthauls, midhauls, backhauls, and/or antenna arrays of the system 160.

FIG. 2A is a timing diagram illustrating a process 200 for beamforming from a sounding reference signal and a delay in applying the beamforming to a physical resource shared channel (PUSCH) uplink transmission. As shown in FIG. 2A, at the outset of process 200, an O-RAN RU (e.g., RU 168 a) receives an SRS transmission from a UE (e.g., UE 170 a) and provides this information to an O-RAN DU (e.g., DU 166 a) for processing and beam generation. In response, the O-RAN DU calculates beam weights and provides the beam weights to the O-RAN RU for use when receiving subsequent PUSCH transmissions from the UE. However, channel conditions may change during the time between the O-RAN RU receiving the SRS transmission and using the SRS-based beam weights at the RU beamformer for uplink reception of user data. This stagnation delay, labelled as delta_s, is known as “beam aging,” which can be problematic in existing split RAN deployments. The back-and-forth (SRS receipt- and processing-related) delay experienced in conventional configurations can result in improper “steering” of beams in “directions” that are no longer valid if a given UE has moved to a different location or if other changing channel conditions (multipath, fading, etc.) occur in the interim.

FIG. 2B depicts a block diagram of an exemplary, non-limiting embodiment of a fronthaul split configuration 201 capable of providing combined beamforming for improved uplink performance in accordance with various aspects described herein. In various embodiments, the configuration may be included in, may function within, or may be operatively overlaid upon the communications network 100 of FIG. 1A and/or the system 160 of FIG. 1B.

As shown in FIG. 2B, the configuration 201 may involve a DU 166 a and an RU 168 a. The DU 166 a may be configured to provide various functions including, but not limited to, DMRS-based equalization 206, demodulation 208, and SRS-based beam designing (or BF weight calculation) 210. The RU 168 a may include an antenna array 202 and may also be configured to provide a variety of functions, including, but not limited to, Fast Fourier Transform (FFT) processing, digital beamforming (or BF filtering) 204, DMRS extraction (or DMRS channel estimation) 214, and DMRS-based beam designing (or BF weight calculation) 216. It is to be appreciated and understood that each of the functions of the DU 166 a and RU 168 a may be implemented in any suitable manner—i.e., in hardware and/or software.

As depicted in FIG. 2B, the DU 166 a may perform SRS-based beam designing (210) (based on SRS data previously received from a UE) and provide generated beams—i.e., beam weights or coefficients—to the RU 168 a over a fronthaul 181 a. These beams may enable digital “steering” of the antenna array 202 to facilitate capturing of the maximum amount of signal power in UE uplink transmissions. Digital “steering” may involve matrix multiplication where beam weights or coefficients control how the beams are formed. As shown, the RU 168 a may update the digital beamformer 204 (matrix) with the beams and may apply digital beamforming on N ‘chains’ of user data (signals received by the antenna array 202 from one or more UEs) to derive P ‘streams’ of information. The P ‘streams’ may be transmitted over the fronthaul 181 a to the DU 166 a and undergo DMRS-based equalization (206), resulting in L ‘layers’ (corresponding to L data channels) sent by the UE(s). The DU 166 a may then demodulate the L ‘layers’ to obtain the corresponding user data.

In an example scenario where the antenna array 202 includes 64 antennas, and where a UE sends two data channels (or layers) to the RU 168 a, the value of P may be anywhere from 2 to 64—or, optionally, higher in cases where signal compression is performed on (e.g., each of the) beams, and thus additional columns (for additional ‘streams’) in the matrix of the digital beamformer 204 may carry additional information should different compression types be used for different columns. Where digital beamformer (204) reduces dimensionality of the antenna array 202 to P ‘streams’ that are less than or equal to N ‘chains’, the burden on the fronthaul 181 a can be reduced.

In massive MIMO, it is important to relieve the fronthaul from the tasks of estimating numerous channels and achieving appropriate beamforming to maintain optimal uplink performance. As briefly described above, beam aging can be problematic in existing split RAN deployments. Configuring the RU 168 a with additional functions 212 (including, e.g., DMRS extraction and channel estimation 214 and DMRS-based beamforming 216) can address the abovementioned beam aging problem, and further enable intelligent allocation of beam designing responsibilities between the DU 166 a and the RU 168 a.

In exemplary embodiments, the RU 168 a configuration leverages DMRS information typically sent along with UE data transmissions to derive the most up-to-date beams for use with digital beamforming. In various embodiments, the RU 168 a may extract such DMRS information (from N ‘chains’), perform channel estimation (214) using the DMRS information, and design DMRS-based beams (216) (using known DMRS beam design algorithm(s) or the like) based on DMRS channel estimates. The RU 168 a may then update the digital beamformer 204 with these beam outputs in conjunction with any SRS-based beams designed by and obtained from the DU 166 a. For instance, the RU 168 a may (e.g., based on a command from the DU 166 a) use SRS-based beam(s) for certain column(s) of the digital beamformer 204's matrix, and use DMRS-based beam(s) for other column(s) of the matrix. In this way, the digital beamformer 204 can leverage the advantages offered by both SRS- and DMRS-based channel estimates to optimize or improve uplink performance. For instance, in an example scenario where the antenna array 202 includes 64 antennas, and where a given UE transmits a single data channel (or layer), the RU 168 a may (e.g., based on a command from the DU 166 a) utilize an SRS-based beam (generated by the DU 166 a) in one column of the digital beamformer 204's matrix, and utilize a DMRS-based beam (generated by the RU 168 a) in another column of the matrix, to derive two streams of data for use by the DU 166 a. Here, the DU 166 a can extract data from both streams and harvest the benefits of both DMRS (which might be a bit noisy but is the most up to date) and SRS (which might be slightly dated but is intensively processed by the DU to reduce noise / eliminate interference).

In exemplary embodiments, the DU 166 a and/or an associated RIC configuration (e.g., the RIC 164 a of FIG. 1B) may dynamically identify the quantity of beams needed for a given UE and determine (and effect) appropriate allocation of beam generation responsibilities between the DU 166 a and the RU 168 a. In various embodiments, the DU 166 a and/or the RIC 164 a may derive performance measurement(s) based on analyzing uplink performance (e.g., signal to interference and noise ratio (SINR) and/or other metrics) associated with use of RU-generated beams (e.g., DMRS-based beams) as compared to DU-generated beams (e.g., SRS-based beams), and employ AI/ML algorithm(s) to determine the appropriate allocation of beam design responsibilities between the DU 166 a and the RU 168 a, such as the frequency of generating and transmitting beamforming data. This enables intelligent (and optimized or improved) load balancing across the fronthaul split 201 in which the burden of (e.g., SRS-based) beam generation on the DU 166 a and transferring of generated (e.g., SRS-based) beams across the fronthaul 181 a may be alleviated in situations where uplink performance is determined to be sufficient (e.g., where SINR and/or other metrics satisfy one or more thresholds), and in which the DU 166 a may instead be tasked with (e.g., SRS-based) beam generation and transmission of generated (e.g., SRS-based) beams over the fronthaul 181 in situations where uplink performance is determined to be insufficient (e.g., where SINR and/or other metrics do not satisfy the one or more thresholds).

In certain embodiments, where several RUs are geographically positioned close to one another such that a given UE's uplink transmissions are received by some or all of these RUs, a corresponding DU (and/or RIC) may, based upon identifying the RUs that are in communication with the UE, effect the aforementioned beam generation allocation across the identified RUs (e.g., in a joint fashion). Here, the DU may or may not be tasked with generating (e.g., SRS-based) beam(s), one or more of the identified RUs may be tasked with generating one or more (e.g., DMRS-based) beams based on subsequent UL transmissions, and each of the various identified RUs may combine any DU-generated beam(s) with that RU's own generated beams to provide overall improved UL reliability for the UE.

In various embodiments, the aforementioned AI/ML algorithm(s) may include classifiers. In certain embodiments, the DU and/or the RIC may train the AI/ML algorithm(s) to perform beam designing/forming responsibility allocations. In some embodiments, the DU and/or the RIC may provide information regarding determined allocations as input to the AI/ML algorithm(s), which may learn to automate future determinations of allocations. For instance, the DU and/or the RIC may train a machine learning algorithm based on known inputs, such as particular user priorities, particular user reliability/latency requirements and/or service level agreements, particular user channel conditions, particular user mobility information, particular content types, particular load(s) on a fronthaul, particular load(s) on the DU, particular loads on the RU, certain network resource usage patterns, instantaneous user loading data, etc. and known outputs, such as beam designing/forming responsibility allocations (e.g., where the DU generates “m” beams based on SRS and the RU generates “n” beams based on DMRS for a given UE, where the DU generates x% of the matrix beams based on SRS and the RU generates a remainder of the matrix beams based on DMRS for a given UE, etc.). In one or more embodiments, the DU and/or the RIC may refine a machine learning algorithm based on feedback received from a user of the DU and/or the RIC and/or from one or more other devices (e.g., management device(s)). In various embodiments, the AI or ML algorithm(s) may be configured to reduce any error in the determinations of allocations. For example, a user of the DU and/or the RIC and/or one or more management devices may provide feedback indicating whether determinations of allocation, made by the machine learning algorithm based on new inputs, are accurate and/or helpful. When the feedback indicates that a particular determination is accurate and/or helpful, the DU and/or the RIC may configure the machine learning algorithm to make determinations of allocation based on the particular determination (e.g., to determine future allocations in a manner similar to that in which the particular determination was made). When the feedback indicates that a particular determination is not accurate or helpful, the DU and/or the RIC may configure the machine learning algorithm to avoid determining allocations in a manner in which the particular determination was made. In this way, any error that may be present may be provided as feedback to the algorithm(s) such that the error may tend to converge toward zero as the algorithm(s) are utilized more and more. Determining allocations based on a machine learning algorithm thus improves the accuracy of the determinations and conserves processor and/or storage resources that may otherwise be used to generate and store rules for determining allocations.

As an example, in a case where the DU 166 a (and/or the RIC 164 a) determines (e.g., using the AI/ML algorithm(s)) that a current load on the fronthaul 181 a satisfies a threshold (e.g., is equal to or greater than a threshold value), the DU 166 a (and/or the RIC 164 a) may (e.g., using the AI/ML algorithm(s)) allocate beam generation responsibilities such that the RU 168 a generates some or all of the beams and the DU 166 a generates few to none of the beams. Continuing the example, in a different case where the DU 166 a (and/or the RIC 164 a) determines (e.g., using the AI/ML algorithm(s)) that the current load on the fronthaul 181 a does not satisfy the threshold (e.g., is less than the threshold value), the DU 166 a (and/or the RIC 164 a) may (e.g., using the AI/ML algorithm(s)) allocate beam generation responsibilities such that the RU 168 a generates few to none of the beams and the DU 166 a generates some or all of the beams.

As some other examples, the DU 166 a (and/or the RIC 164 a) may (e.g., using the AI/ML algorithm(s)) allocate beam generation responsibilities based on user priority (e.g., where beamforming may be effected using both DMRS- and SRS-based beams if a user priority satisfies (e.g., exceeds) a threshold or where beamforming may be effected using only SRS-based beams or only DMRS-based beams if a user priority does not satisfy (e.g., does not exceed) the threshold), based on user reliability/latency requirements and/or service level agreements (e.g., where beamforming may be effected using both DMRS- and SRS-based beams if a UE is associated with a first responder or where beamforming may be effected using only SRS-based beams or only DMRS-based beams for other UEs not associated with a first responder), user channel conditions and/or mobility (e.g., where beamforming may be effected using both DMRS- and SRS-based beams if a change in channel condition or a speed of movement of a UE satisfies (e.g., exceeds) one or more thresholds or where beamforming may be effected using only SRS-based beams or only DMRS-based beams if a change in channel condition or a speed of movement of a UE does not satisfy (e.g., does not exceed) the one or more thresholds), content type (e.g., where beamforming may be effected using both DMRS- and SRS-based beams if the content type for a UE is of a certain type or where beamforming may be effected using only SRS-based beams or only DMRS-based beams if the content type for a UE is not of the certain type), etc.

FIG. 2C illustrates various example beam designing/forming responsibility allocations in accordance with various aspects described herein. In example 222, the beamforming matrix may include DMRS BF weight columns that are concatenated with some SRS BF weight columns. Here, one or more ML algorithms of the DU 166 a and/or the RIC 164 a may (e.g., based on DMRS channel estimates and/or DMRS-based BF weight calculations at the RU 168 a exceeding noise-related threshold(s)) determine that it is useful to rely on a few SRS-based beams. In this case, the DU 166 a may generate one or more SRS BF weight columns for concatenation to the digital beamforming matrix 204. For instance, for N=64 and P=16, the beamforming matrix 204 of FIG. 2B may be populated with mostly DMRS BF weight columns (e.g., 13 of 16 total columns may be DMRS BF weight columns) that are augmented with several SRS BF weight columns (e.g., 3 of the columns may be SRS BF weight columns).

In example 224 of FIG. 2C, the beamforming matrix may include only DMRS BF weight columns. Here, one or more ML algorithms of the DU 166 a and/or the RIC 164 a may (e.g., based on DMRS channel estimates and/or DMRS-based BF weight calculations at the RU 168 a not exceeding noise-related threshold(s)) determine that there is no need for SRS-based beams. In this case, the RU 168 a may be instructed to generate all of the BF weight columns of the digital beamforming matrix 204. For instance, for N=64 and P=16, the beamforming matrix may be populated with only DMRS BF weight columns (e.g., 16 of 16 total columns may be DMRS BF weight columns).

In example 226 of FIG. 2C, multiple RUs 168 a may be connected to a DU 166 a, where UL info from a given UE 170 a is received by the DU 166 a via those RUs 168 a. As the DU 166 a in this example has access to information from all of the multiple RUs 168 a, the DU 166 a may be able to compute BF weights that are jointly optimized and reliable. Here, one or more ML algorithms of the DU 166 a and/or the RIC 164 a may (e.g., based on the DU 166 a having access to information from all of the multiple RUs 168 a and based on certain elements of the information satisfying threshold(s)) determine that SRS-based BF weights are important. In this case, the DU 166 a may generate most of the BF weight columns for the digital beamforming matrix 204 in each of some or all of the multiple RUs 168 a, and each of some or all of the multiple RUs 168 a may generate only a few SRS-based beams. For instance, for N=64 and P=16, the beamforming matrix 204 at each of some or all of the multiple RUs 168 a may be populated with mostly SRS BF weight columns (e.g., 14 or 15 of 16 total columns may be SRS BF weight columns) that are augmented with some DMRS BF weight columns (e.g., 1 or 2 of the columns may be DMRS BF weight columns).

As described in more detail below, one or more embodiments can include SRS data compression from RU to DU using beam space compression. That is, SRS data can be compressed to save on the fronthaul throughput. As also described below, other embodiments can include SRS channel estimates compression from DU to RU that comprise two aspects. The first aspect includes added information by sending SRS channel estimates back to the RU to help with DMRS weight calculations. The second aspect includes using beam space compression to send that information back to the RU to save on fronthaul throughput. Further embodiments can include DMRS channel estimate compression from RU to the DU. That is, the DMRS channel estimates extracted at the RU can be sent to the scheduler to help improve scheduling decisions and policy decisions regarding the concatenation of DMRS and SRS information. The DMRS channel estimates can be compressed using beam space compression to save on fronthaul throughput.

Exemplary embodiments provide for allocation of channel information transfer for enhancing massive MIMO uplink performance in split RAN deployments.

In various embodiments, DMRS and SRS channel estimates may be exchanged between a DU and an RU to facilitate generation of optimal or improved (or “good”) beams. FIG. 2D is a block diagram illustrating an example, non-limiting embodiment of a system functioning within, or operatively overlaid upon, the communications network 100 of FIG. 1A and/or the system 160 of FIG. 1B in accordance with various aspects described herein. In exemplary embodiments, the system of FIG. 2D may be similar to the system of FIG. 2B, but may include additional blocks/functionality (e.g., 232, 234) for the exchange of DMRS and/or SRS channel estimates. In various embodiments, the system of FIG. 2D may be capable of judicially using the SRS and DMRS estimates that are transferred between the RU 168 a and the DU 166 a, depending on user information and conditions, to optimize the use of the fronthaul. In the case of DMRS channel estimates, the DU 166 a may submit request(s) to the RU 168 a for DMRS channel estimates relating to UEs 170 a that have strict reliability and latency requirements (e.g., those that exceed certain threshold(s)) and may or may not submit request(s) for DMRS channel estimates relating to other UEs 170 a that do not have such high reliability requirements. In various embodiments, RIC-based policies associated with controls, such as channel conditions, mobility information, reliability, latency, 5QI, etc., for UEs may dictate whether the DU 166 a submits requests to the RU 168 a for DMRS channel estimates. In the case of SRS channel estimates, the DU 166 a (and/or the RIC 164 a) may decide whether to send this information to the RU 168 a for UEs 170 a that have strict latency and reliability requirements (e.g., those that exceed certain threshold(s)). In various embodiments, RIC-based policies associated with controls, such as channel conditions, mobility information, reliability, latency, 5QI, etc., for UEs 170 a may similarly dictate whether the DU 166 a sends SRS channel estimates to the RU 168 a. In this way, the DU 166 a (e.g., a scheduler therein) can leverage DMRS information (which can include DMRS resource elements and/or DMRS channel estimates) to optimize or improve its SRS-based beam generation (e.g., the scheduler can utilize the DMRS information to improve scheduling decisions and/or policy decisions regarding concatenation of DMRS and SRS information), and an RU 168 a can similarly leverage SRS information (e.g., SRS channel estimates) to optimize or improve its DMRS-based beam generation (i.e., to aid in DMRS weight calculations).

Depending on the network or computational load, benefits from the exchange of DMRS and SRS channel estimates can come at the cost of spent fronthaul throughput. Thus, the exchanges may need to be weighed against any potential communication performance gain that might come from beamforming improvement.

In various embodiments, fronthaul throughput may be flexibly optimized or improved based on intelligent selection of physical control data, given a large antenna space. To optimize or improve usage of fronthaul capacity, in an embodiment, a DU (and/or a RIC) may be configured to instruct the RU to enable or disable calculation and/or transmission of DMRS channel estimates from the RU. In another embodiment, the DU and/or RIC may be configured to enable or disable transmission of SRS information (e.g., channel estimates) to the RU. Additionally, or alternatively, the DU (and/or the RIC) may be configured to determine how frequently DMRS channel estimates are received from an RU and/or determine how frequently SRS information is transmitted to the RU. Further, the DU (and/or the RIC) may additionally, or alternatively, be configured to determine which UE(s) require the RU to determine and transmit DMRS channel estimates. Furthermore, the DU (and/or the RIC) may additionally, or alternatively, be configured to determine the UE(s) for which SRS information is to be transmitted to the RU. Some or all of these aforementioned determinations may be performed using AI/ML algorithm(s) based on one or more inputs, including, for example, data regarding user priority, user reliability/latency requirements and/or service level agreements, user channel conditions, user mobility, content type, load on the fronthaul, load on the DU, load on the RU, network resource usage patterns, instantaneous user loading, etc. The DU (and/or the RIC) may thus make decisions regarding the exchange of DMRS channel estimates and SRS channel estimates over the fronthaul, either separately or jointly. Joint optimization may be performed to maximize UL performance metrics (e.g., average throughput, cell edge throughput, and/or other metrics for different types of traffic and different types of users) with an overall constraint on fronthaul capacity and overhead, and taking into account user loading, traffic patterns, traffic trend information, etc.

In this way, a DU (and/or RIC) can control how much channel estimate information it provides to an RU for the RU to improve its beamforming algorithm and how much channel estimate information it receives from the RU for the DU to improve its own beamforming algorithm.

Exemplary embodiments thus provide a novel mechanism for an O-RAN DU (and/or RIC) to adjust the amount of control information that passes between the DU and an RU, which can maximize the use of available fronthaul capacity in the face of changing network load scenarios. Fronthaul capacity can be preserved as needed, and compression may be applied to certain control information accordingly.

As discussed above, a DU can leverage DMRS information (which can include DMRS resource elements and/or DMRS channel estimates) to facilitate generation of optimal or improved (or “good”) beams, and an RU can similarly leverage SRS information (e.g., SRS channel estimates) to optimize or improve its own beam generation and/or beamforming. However, transferring reference real/imaginary (I/Q) data or channel estimates spends fronthaul throughput, and can thus overshadow or undermine any improvement in performance that might result from the above-described combined beamforming techniques.

In exemplary embodiments, therefore, the DU and/or the RU may employ compression algorithm(s) on reference I/Q and/or channel estimate data so as to reduce the impact on fronthaul throughput. As these types of data share the same property (i.e., they are generally low-dimensional data in a large dimensional signal), they can be compressed in similar manners. Appropriate counterpart decompression algorithm(s) may also be employed to decompress the data.

In various embodiments, a (e.g., known or existing) beamspace compression algorithm, that might not be specified for use with compressing channel estimates or reference signal IQ data, may nevertheless be used in various implementations of the split fronthaul configuration.

In one or more embodiments, and referring to FIG. 2D, the DU 166 a may employ one or more beamspace compression algorithms to compress SRS-based beams (e.g., outputs of 210) and/or SRS channel estimates (e.g., compression block 232) prior to transmission thereof to RU 168 a over the fronthaul 181 a. In certain embodiments, the RU 168 a may employ one or more counterpart decompression algorithms to obtain the SRS-based beams and/or SRS channel estimates and utilize the SRS-based beams in digital beamforming (e.g., 204) and/or utilize the SRS channel estimates to improve its DMRS-based beam designs (e.g., 216). In various embodiments, the RU 168 a may utilize presently received SRS channel estimates and/or historical (previously received) SRS channel estimates to generate beams.

In one or more embodiments, the RU 168 a may employ one or more beamspace compression algorithms (e.g., compression block 230) to compress SRS data (e.g., in N ‘chains’) received by the antenna array 202, prior to transmission thereof to the DU 166 a over the fronthaul 181 a. In certain embodiments, the DU 166 a may employ one or more counterpart decompression algorithms to obtain the SRS data and utilize this SRS data to derive SRS channel estimates for improving its beam designs. In various embodiments, the DU 166 a may utilize presently received SRS data and/or historical (previously received) SRS data to generate beams.

In one or more embodiments, the RU 168 a may employ one or more beamspace compression algorithms to compress DMRS-based beams (e.g., outputs of 216) and/or DMRS channel estimates (e.g., compression block 234) prior to transmission thereof to the DU 166 a over the fronthaul 181 a. In certain embodiments, the DU 166 a may employ one or more counterpart decompression algorithms to obtain the DMRS-based beams and/or DMRS channel estimates and utilize the DMRS-based beams in its SRS-based beam designing (e.g., 210) and/or utilize the DMRS channel estimates to improve its SRS-based beam designs (e.g., 210). In various embodiments, the DU 166 a may utilize presently received DMRS channel estimates and/or historical (previously received) DMRS channel estimates to generate beams.

In this way, channel agnostic compression algorithm(s) (e.g., based on beamspace compression) can be used to compress DMRS and/or SRS channel estimates prior to being exchanged between a DU and an RU over a fronthaul. The efficiency of beamspace compression enables reduced traffic load on the fronthaul, thereby providing improved split RAN deployments.

It is to be understood and appreciated that the functions represented by blocks 230, 232, 234 in FIG. 2D can be added individually—e.g. there can be one or multiple of these beam space compression functions represented in blocks.

Exemplary embodiments thus provide a novel mechanism for compressing reference signals and/or channel estimates (prior to transmission over a fronthaul) in a split RAN architecture, where improved uplink performance can be achieved in massive MIMO deployments.

In various embodiments, the RIC portions 164 a-1 and/or 164 a-2 may, depending on the application, leverage controls from the DU 166 a (and/or the CU 174 a) to create policies for the (e.g., Layer 2) scheduler in the DU 166 a. The scheduler may utilize the policies to decide on DMRS and SRS beamforming weights concatenation so as to improve fronthaul UL performance. The controls may relate to channel conditions (or a histogram of the channel quality information), traffic information/buffer/load per user, mobility information, reliability/latency requirements, service level agreements (SLAs) per user, usage information, traffic patterns, and/or the like. In certain embodiments, the policies (e.g., concerning weight allocations, number of streams per users, etc.) may dictate how/whether to use the SRS at the DU 166 a and the DMRS at the RU 168 a to create the digital beamforming weights at the RU for different paired users that are transmitting to the RUs 168 a.

It is to be understood and appreciated that the quantity and arrangement of units and blocks/components shown in each of FIGS. 2B and 2D are provided as an example. In practice, there may be additional units and/or blocks/components, fewer units and/or blocks/components, different units and/or blocks/components, or differently arranged units and/or blocks/components than those shown in FIGS. 2B and 2D. For example, the system can include more or fewer units and/or blocks/components, etc. In practice, therefore, there can be hundreds, thousands, millions, billions, etc. of such units and/or blocks/components. In this way, the example system can coordinate, or operate in conjunction with, a set of units and/or blocks/components and/or operate on data sets that cannot be managed manually or objectively by a human actor. Furthermore, two or more units or blocks/components shown in any of FIGS. 2B and 2D may be implemented within a single unit or block/component, or a single unit or block/component shown in any of FIGS. 2B and 2D may be implemented as multiple units or blocks/components. Additionally, or alternatively, a set of units or blocks/components of the system may perform one or more functions described as being performed by another set of units or blocks/components of the system.

It is also to be understood and appreciated that, although one or more of FIGS. 2B-2D is described above as pertaining to various processes and/or actions that are performed in a particular order, some of these processes and/or actions may occur in different orders and/or concurrently with other processes and/or actions from what is depicted and described above. Moreover, not all of these processes and/or actions may be required to implement the systems and/or methods described herein.

In various embodiments, threshold(s) may be utilized as part of determining/identifying one or more actions to be taken or engaged. The threshold(s) may be adaptive based on an occurrence of one or more events or satisfaction of one or more conditions (or, analogously, in an absence of an occurrence of one or more events or in an absence of satisfaction of one or more conditions).

FIG. 2E depicts an illustrative embodiment of a method 250 in accordance with various aspects described herein.

At 252, the method can include generating first beam weights by a first processor of a distributed unit (DU) in a network—e.g., similar to that described above with respect to FIGS. 2B and/or 2D.

At 254, the method can include transmitting, by the first processor, the first beam weights to a remote unit (RU) of the network, wherein the DU and the RU are communicatively coupled to one another via a split fronthaul—e.g., similar to that described above with respect to FIGS. 2B and/or 2D.

At 256, the method can include generating second beam weights by a second processor of the RU—e.g., similar to that described above with respect to FIGS. 2B and/or 2D.

At 258, the method can include performing digital beamforming for an uplink of the network based on the first beam weights and the second beam weights—e.g., similar to that described above with respect to FIGS. 2B and/or 2D.

In some implementations of these embodiments, the generating the first beam weights is based on sounding reference signal (SRS) data.

In some implementations of these embodiments, the generating the second beam weights is based on demodulation reference signal (DMRS) data.

In some implementations of these embodiments, the network comprises a radio access network (RAN) intelligent controller (RIC).

In some implementations of these embodiments, the method further comprises determining, by the first processor of the DU or by the RIC, a performance of the uplink, and allocating beam generation tasks between the DU and the RU based on the performance.

While for purposes of simplicity of explanation, the respective processes are shown and described as a series of blocks in FIG. 2E, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks may be required to implement the methods described herein.

Referring now to FIG. 3 , a block diagram 300 is shown illustrating an example, non-limiting embodiment of a virtualized communications network in accordance with various aspects described herein. In particular, a virtualized communications network is presented that can be used to implement some or all of the subsystems and functions of system 100 of FIG. 1A, the subsystems and functions of system 160 of FIG. 1B, the subsystems and functions of the system of FIG. 2B, and the subsystems and functions shown in FIG. 2D. For example, virtualized communications network 300 can facilitate, in whole or in part, combined beamforming, channel information transfer allocation, and/or reference signal compression for massive MIMO uplink enhancement in wireless RANs deployed with a fronthaul split or any other lower, physical layer split.

In particular, a cloud networking architecture is shown that leverages cloud technologies and supports rapid innovation and scalability via a transport layer 350, a virtualized network function cloud 325 and/or one or more cloud computing environments 375. In various embodiments, this cloud networking architecture is an open architecture that leverages application programming interfaces (APIs); reduces complexity from services and operations; supports more nimble business models; and rapidly and seamlessly scales to meet evolving customer requirements including traffic growth, diversity of traffic types, and diversity of performance and reliability expectations.

In contrast to traditional network elements—which are typically integrated to perform a single function, the virtualized communications network employs virtual network elements (VNEs) 330, 332, 334, etc. that perform some or all of the functions of network elements 150, 152, 154, 156, etc. For example, the network architecture can provide a substrate of networking capability, often called Network Function Virtualization Infrastructure (NFVI) or simply infrastructure that is capable of being directed with software and Software Defined Networking (SDN) protocols to perform a broad variety of network functions and services. This infrastructure can include several types of substrates. The most typical type of substrate being servers that support Network Function Virtualization (NFV), followed by packet forwarding capabilities based on generic computing resources, with specialized network technologies brought to bear when general-purpose processors or general-purpose integrated circuit devices offered by merchants (referred to herein as merchant silicon) are not appropriate. In this case, communication services can be implemented as cloud-centric workloads.

As an example, a traditional network element 150 (shown in FIG. 1A), such as an edge router can be implemented via a VNE 330 composed of NFV software modules, merchant silicon, and associated controllers. The software can be written so that increasing workload consumes incremental resources from a common resource pool, and moreover so that it is elastic: so, the resources are only consumed when needed. In a similar fashion, other network elements such as other routers, switches, edge caches, and middle-boxes are instantiated from the common resource pool. Such sharing of infrastructure across a broad set of uses makes planning and growing infrastructure easier to manage.

In an embodiment, the transport layer 350 includes fiber, cable, wired and/or wireless transport elements, network elements and interfaces to provide broadband access 110, wireless access 120, voice access 130, media access 140 and/or access to content sources 175 for distribution of content to any or all of the access technologies. In particular, in some cases a network element needs to be positioned at a specific place, and this allows for less sharing of common infrastructure. Other times, the network elements have specific physical layer adapters that cannot be abstracted or virtualized and might require special DSP code and analog front ends (AFEs) that do not lend themselves to implementation as VNEs 330, 332 or 334. These network elements can be included in transport layer 350.

The virtualized network function cloud 325 interfaces with the transport layer 350 to provide the VNEs 330, 332, 334, etc. to provide specific NFVs. In particular, the virtualized network function cloud 325 leverages cloud operations, applications, and architectures to support networking workloads. The virtualized network elements 330, 332 and 334 can employ network function software that provides either a one-for-one mapping of traditional network element function or alternately some combination of network functions designed for cloud computing. For example, VNEs 330, 332 and 334 can include route reflectors, domain name system (DNS) servers, and dynamic host configuration protocol (DHCP) servers, system architecture evolution (SAE) and/or mobility management entity (MME) gateways, broadband network gateways, IP edge routers for IP-VPN, Ethernet and other services, load balancers, distributers and other network elements. Because these elements do not typically need to forward substantial amounts of traffic, their workload can be distributed across a number of servers—each of which adds a portion of the capability, and which creates an overall elastic function with higher availability than its former monolithic version. These virtual network elements 330, 332, 334, etc. can be instantiated and managed using an orchestration approach similar to those used in cloud compute services.

The cloud computing environments 375 can interface with the virtualized network function cloud 325 via APIs that expose functional capabilities of the VNEs 330, 332, 334, etc. to provide the flexible and expanded capabilities to the virtualized network function cloud 325. In particular, network workloads may have applications distributed across the virtualized network function cloud 325 and cloud computing environment 375 and in the commercial cloud or might simply orchestrate workloads supported entirely in NFV infrastructure from these third-party locations.

Turning now to FIG. 4 , there is illustrated a block diagram of a computing environment in accordance with various aspects described herein. To provide additional context for various embodiments of the embodiments described herein, FIG. 4 and the following discussion are intended to provide a brief, general description of a suitable computing environment 400 in which the various embodiments of the subject disclosure can be implemented. In particular, computing environment 400 can be used in the implementation of network elements 150, 152, 154, 156, access terminal 112, base station or access point 122, switching device 132, media terminal 142, and/or VNEs 330, 332, 334, etc. Each of these devices can be implemented via computer-executable instructions that can run on one or more computers, and/or in combination with other program modules and/or as a combination of hardware and software. For example, computing environment 400 can facilitate, in whole or in part, combined beamforming, channel information transfer allocation, and/or reference signal compression for massive MIMO uplink enhancement in wireless RANs deployed with a fronthaul split or any other lower, physical layer split.

Generally, program modules comprise routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the methods can be practiced with other computer system configurations, comprising single-processor or multiprocessor computer systems, minicomputers, mainframe computers, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.

As used herein, a processing circuit includes one or more processors as well as other application specific circuits such as an application specific integrated circuit, digital logic circuit, state machine, programmable gate array or other circuit that processes input signals or data and that produces output signals or data in response thereto. It should be noted that while any functions and features described herein in association with the operation of a processor could likewise be performed by a processing circuit.

The illustrated embodiments of the embodiments herein can be also practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

Computing devices typically comprise a variety of media, which can comprise computer-readable storage media and/or communications media, which two terms are used herein differently from one another as follows. Computer-readable storage media can be any available storage media that can be accessed by the computer and comprises both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable instructions, program modules, structured data or unstructured data.

Computer-readable storage media can comprise, but are not limited to, random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM),flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or other tangible and/or non-transitory media which can be used to store desired information. In this regard, the terms “tangible” or “non-transitory” herein as applied to storage, memory or computer-readable media, are to be understood to exclude only propagating transitory signals per se as modifiers and do not relinquish rights to all standard storage, memory or computer-readable media that are not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local or remote computing devices, e.g., via access requests, queries or other data retrieval protocols, for a variety of operations with respect to the information stored by the medium.

Communications media typically embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and comprises any information delivery or transport media. The term “modulated data signal” or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media comprise wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 4 , the example environment can comprise a computer 402, the computer 402 comprising a processing unit 404, a system memory 406 and a system bus 408. The system bus 408 couples system components including, but not limited to, the system memory 406 to the processing unit 404. The processing unit 404 can be any of various commercially available processors. Dual microprocessors and other multiprocessor architectures can also be employed as the processing unit 404.

The system bus 408 can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory 406 comprises ROM 410 and RAM 412. A basic input/output system (BIOS) can be stored in a non-volatile memory such as ROM, erasable programmable read only memory (EPROM), EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer 402, such as during startup. The RAM 412 can also comprise a high-speed RAM such as static RAM for caching data.

The computer 402 further comprises an internal hard disk drive (HDD) 414 (e.g., EIDE, SATA), which internal HDD 414 can also be configured for external use in a suitable chassis (not shown), a magnetic floppy disk drive (FDD) 416, (e.g., to read from or write to a removable diskette 418) and an optical disk drive 420, (e.g., reading a CD-ROM disk 422 or, to read from or write to other high capacity optical media such as the DVD). The HDD 414, magnetic FDD 416 and optical disk drive 420 can be connected to the system bus 408 by a hard disk drive interface 424, a magnetic disk drive interface 426 and an optical drive interface 428, respectively. The hard disk drive interface 424 for external drive implementations comprises at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external drive connection technologies are within contemplation of the embodiments described herein.

The drives and their associated computer-readable storage media provide nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For the computer 402, the drives and storage media accommodate the storage of any data in a suitable digital format. Although the description of computer-readable storage media above refers to a hard disk drive (HDD), a removable magnetic diskette, and a removable optical media such as a CD or DVD, it should be appreciated by those skilled in the art that other types of storage media which are readable by a computer, such as zip drives, magnetic cassettes, flash memory cards, cartridges, and the like, can also be used in the example operating environment, and further, that any such storage media can contain computer-executable instructions for performing the methods described herein.

A number of program modules can be stored in the drives and RAM 412, comprising an operating system 430, one or more application programs 432, other program modules 434 and program data 436. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM 412. The systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems.

A user can enter commands and information into the computer 402 through one or more wired/wireless input devices, e.g., a keyboard 438 and a pointing device, such as a mouse 440. Other input devices (not shown) can comprise a microphone, an infrared (IR) remote control, a joystick, a game pad, a stylus pen, touch screen or the like. These and other input devices are often connected to the processing unit 404 through an input device interface 442 that can be coupled to the system bus 408, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a universal serial bus (USB) port, an IR interface, etc.

A monitor 444 or other type of display device can be also connected to the system bus 408 via an interface, such as a video adapter 446. It will also be appreciated that in alternative embodiments, a monitor 444 can also be any display device (e.g., another computer having a display, a smart phone, a tablet computer, etc.) for receiving display information associated with computer 402 via any communication means, including via the Internet and cloud-based networks. In addition to the monitor 444, a computer typically comprises other peripheral output devices (not shown), such as speakers, printers, etc.

The computer 402 can operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, such as a remote computer(s) 448. The remote computer(s) 448 can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically comprises many or all of the elements described relative to the computer 402, although, for purposes of brevity, only a remote memory/storage device 450 is illustrated. The logical connections depicted comprise wired/wireless connectivity to a local area network (LAN) 452 and/or larger networks, e.g., a wide area network (WAN) 454. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 402 can be connected to the LAN 452 through a wired and/or wireless communications network interface or adapter 456. The adapter 456 can facilitate wired or wireless communication to the LAN 452, which can also comprise a wireless AP disposed thereon for communicating with the adapter 456.

When used in a WAN networking environment, the computer 402 can comprise a modem 458 or can be connected to a communications server on the WAN 454 or has other means for establishing communications over the WAN 454, such as by way of the Internet. The modem 458, which can be internal or external and a wired or wireless device, can be connected to the system bus 408 via the input device interface 442. In a networked environment, program modules depicted relative to the computer 402 or portions thereof, can be stored in the remote memory/storage device 450. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.

The computer 402 can be operable to communicate with any wireless devices or entities operatively disposed in wireless communication, e.g., a printer, scanner, desktop and/or portable computer, portable data assistant, communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, restroom), and telephone. This can comprise Wireless Fidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices.

Wi-Fi can allow connection to the Internet from a couch at home, a bed in a hotel room or a conference room at work, without wires. Wi-Fi is a wireless technology similar to that used in a cell phone that enables such devices, e.g., computers, to send and receive data indoors and out; anywhere within the range of a base station. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b, g, n, ac, ag, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wired networks (which can use IEEE 802.3 or Ethernet). Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands for example or with products that contain both bands (dual band), so the networks can provide real-world performance similar to the basic 10BaseT wired Ethernet networks used in many offices.

Turning now to FIG. 5 , an embodiment 500 of a mobile network platform 510 is shown that is an example of network elements 150, 152, 154, 156, and/or VNEs 330, 332, 334, etc. For example, platform 510 can facilitate, in whole or in part, combined beamforming, channel information transfer allocation, and/or reference signal compression for massive MIMO uplink enhancement in wireless RANs deployed with a fronthaul split or any other lower, physical layer split. In one or more embodiments, the mobile network platform 510 can generate and receive signals transmitted and received by base stations or access points such as base station or access point 122. Generally, mobile network platform 510 can comprise components, e.g., nodes, gateways, interfaces, servers, or disparate platforms, which facilitate both packet-switched (PS) (e.g., internet protocol (IP), frame relay, asynchronous transfer mode (ATM)) and circuit-switched (CS) traffic (e.g., voice and data), as well as control generation for networked wireless telecommunication. As a non-limiting example, mobile network platform 510 can be included in telecommunications carrier networks and can be considered carrier-side components as discussed elsewhere herein. Mobile network platform 510 comprises CS gateway node(s) 512 which can interface CS traffic received from legacy networks like telephony network(s) 540 (e.g., public switched telephone network (PSTN), or public land mobile network (PLMN)) or a signaling system #7 (SS7) network 560. CS gateway node(s) 512 can authorize and authenticate traffic (e.g., voice) arising from such networks. Additionally, CS gateway node(s) 512 can access mobility, or roaming, data generated through SS7 network 560; for instance, mobility data stored in a visited location register (VLR), which can reside in memory 530. Moreover, CS gateway node(s) 512 interfaces CS-based traffic and signaling and PS gateway node(s) 518. As an example, in a 3GPP UMTS network, CS gateway node(s) 512 can be realized at least in part in gateway GPRS support node(s) (GGSN). It should be appreciated that functionality and specific operation of CS gateway node(s) 512, PS gateway node(s) 518, and serving node(s) 516, is provided and dictated by radio technology(ies) utilized by mobile network platform 510 for telecommunication over a radio access network 520 with other devices, such as a radiotelephone 575.

In addition to receiving and processing CS-switched traffic and signaling, PS gateway node(s) 518 can authorize and authenticate PS-based data sessions with served mobile devices. Data sessions can comprise traffic, or content(s), exchanged with networks external to the mobile network platform 510, like wide area network(s) (WANs) 550, enterprise network(s) 570, and service network(s) 580, which can be embodied in local area network(s) (LANs), can also be interfaced with mobile network platform 510 through PS gateway node(s) 518. It is to be noted that WANs 550 and enterprise network(s) 570 can embody, at least in part, a service network(s) like IP multimedia subsystem (IMS). Based on radio technology layer(s) available in technology resource(s) or radio access network 520, PS gateway node(s) 518 can generate packet data protocol contexts when a data session is established; other data structures that facilitate routing of packetized data also can be generated. To that end, in an aspect, PS gateway node(s) 518 can comprise a tunnel interface (e.g., tunnel termination gateway (TTG) in 3GPP UMTS network(s) (not shown)) which can facilitate packetized communication with disparate wireless network(s), such as Wi-Fi networks.

In embodiment 500, mobile network platform 510 also comprises serving node(s) 516 that, based upon available radio technology layer(s) within technology resource(s) in the radio access network 520, convey the various packetized flows of data streams received through PS gateway node(s) 518. It is to be noted that for technology resource(s) that rely primarily on CS communication, server node(s) can deliver traffic without reliance on PS gateway node(s) 518; for example, server node(s) can embody at least in part a mobile switching center. As an example, in a 3GPP UMTS network, serving node(s) 516 can be embodied in serving GPRS support node(s) (SGSN).

For radio technologies that exploit packetized communication, server(s) 514 in mobile network platform 510 can execute numerous applications that can generate multiple disparate packetized data streams or flows, and manage (e.g., schedule, queue, format . . . ) such flows. Such application(s) can comprise add-on features to standard services (for example, provisioning, billing, customer support . . . ) provided by mobile network platform 510. Data streams (e.g., content(s) that are part of a voice call or data session) can be conveyed to PS gateway node(s) 518 for authorization/authentication and initiation of a data session, and to serving node(s) 516 for communication thereafter. In addition to application server, server(s) 514 can comprise utility server(s), a utility server can comprise a provisioning server, an operations and maintenance server, a security server that can implement at least in part a certificate authority and firewalls as well as other security mechanisms, and the like. In an aspect, security server(s) secure communication served through mobile network platform 510 to ensure network's operation and data integrity in addition to authorization and authentication procedures that CS gateway node(s) 512 and PS gateway node(s) 518 can enact. Moreover, provisioning server(s) can provision services from external network(s) like networks operated by a disparate service provider; for instance, WAN 550 or Global Positioning System (GPS) network(s) (not shown). Provisioning server(s) can also provision coverage through networks associated to mobile network platform 510 (e.g., deployed and operated by the same service provider), such as distributed antenna networks that enhance wireless service coverage by providing more network coverage.

It is to be noted that server(s) 514 can comprise one or more processors configured to confer at least in part the functionality of mobile network platform 510. To that end, the one or more processors can execute code instructions stored in memory 530, for example. It should be appreciated that server(s) 514 can comprise a content manager, which operates in substantially the same manner as described hereinbefore.

In example embodiment 500, memory 530 can store information related to operation of mobile network platform 510. Other operational information can comprise provisioning information of mobile devices served through mobile network platform 510, subscriber databases; application intelligence, pricing schemes, e.g., promotional rates, flat-rate programs, couponing campaigns; technical specification(s) consistent with telecommunication protocols for operation of disparate radio, or wireless, technology layers; and so forth. Memory 530 can also store information from at least one of telephony network(s) 540, WAN 550, SS7 network 560, or enterprise network(s) 570. In an aspect, memory 530 can be, for example, accessed as part of a data store component or as a remotely connected memory store.

To provide a context for the various aspects of the disclosed subject matter, FIG. 5 , and the following discussion, are intended to provide a brief, general description of a suitable environment in which the various aspects of the disclosed subject matter can be implemented. While the subject matter has been described above in the general context of computer-executable instructions of a computer program that runs on a computer and/or computers, those skilled in the art will recognize that the disclosed subject matter also can be implemented in combination with other program modules. Generally, program modules comprise routines, programs, components, data structures, etc. that perform particular tasks and/or implement particular abstract data types.

Turning now to FIG. 6 , an illustrative embodiment of a communication device 600 is shown. The communication device 600 can serve as an illustrative embodiment of devices such as data terminals 114, mobile devices 124, vehicle 126, display devices 144 or other client devices for communication via communications network 125. For example, computing device 600 can facilitate, in whole or in part, combined beamforming, channel information transfer allocation, and/or reference signal compression for massive MIMO uplink enhancement in wireless RANs deployed with a fronthaul split or any other lower, physical layer split.

The communication device 600 can comprise a wireline and/or wireless transceiver 602 (herein transceiver 602), a user interface (UI) 604, a power supply 614, a location receiver 616, a motion sensor 618, an orientation sensor 620, and a controller 606 for managing operations thereof. The transceiver 602 can support short-range or long-range wireless access technologies such as Bluetooth®, ZigBee®, Wi-Fi, DECT, or cellular communication technologies, just to mention a few (Bluetooth® and ZigBee® are trademarks registered by the Bluetooth® Special Interest Group and the ZigBee® Alliance, respectively). Cellular technologies can include, for example, CDMA-1X, UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO, WiMAX, SDR, LTE, as well as other next generation wireless communication technologies as they arise. The transceiver 602 can also be adapted to support circuit-switched wireline access technologies (such as PSTN), packet-switched wireline access technologies (such as TCP/IP, VoIP, etc.), and combinations thereof.

The UI 604 can include a depressible or touch-sensitive keypad 608 with a navigation mechanism such as a roller ball, a joystick, a mouse, or a navigation disk for manipulating operations of the communication device 600. The keypad 608 can be an integral part of a housing assembly of the communication device 600 or an independent device operably coupled thereto by a tethered wireline interface (such as a USB cable) or a wireless interface supporting for example Bluetooth®. The keypad 608 can represent a numeric keypad commonly used by phones, and/or a QWERTY keypad with alphanumeric keys. The UI 604 can further include a display 610 such as monochrome or color LCD (Liquid Crystal Display), OLED (Organic Light Emitting Diode) or other suitable display technology for conveying images to an end user of the communication device 600. In an embodiment where the display 610 is touch-sensitive, a portion or all of the keypad 608 can be presented by way of the display 610 with navigation features.

The display 610 can use touch screen technology to also serve as a user interface for detecting user input. As a touch screen display, the communication device 600 can be adapted to present a user interface having graphical user interface (GUI) elements that can be selected by a user with a touch of a finger. The display 610 can be equipped with capacitive, resistive or other forms of sensing technology to detect how much surface area of a user's finger has been placed on a portion of the touch screen display. This sensing information can be used to control the manipulation of the GUI elements or other functions of the user interface. The display 610 can be an integral part of the housing assembly of the communication device 600 or an independent device communicatively coupled thereto by a tethered wireline interface (such as a cable) or a wireless interface.

The UI 604 can also include an audio system 612 that utilizes audio technology for conveying low volume audio (such as audio heard in proximity of a human ear) and high-volume audio (such as speakerphone for hands free operation). The audio system 612 can further include a microphone for receiving audible signals of an end user. The audio system 612 can also be used for voice recognition applications. The UI 604 can further include an image sensor 613 such as a charged coupled device (CCD) camera for capturing still or moving images.

The power supply 614 can utilize common power management technologies such as replaceable and rechargeable batteries, supply regulation technologies, and/or charging system technologies for supplying energy to the components of the communication device 600 to facilitate long-range or short-range portable communications. Alternatively, or in combination, the charging system can utilize external power sources such as DC power supplied over a physical interface such as a USB port or other suitable tethering technologies.

The location receiver 616 can utilize location technology such as a global positioning system (GPS) receiver capable of assisted GPS for identifying a location of the communication device 600 based on signals generated by a constellation of GPS satellites, which can be used for facilitating location services such as navigation. The motion sensor 618 can utilize motion sensing technology such as an accelerometer, a gyroscope, or other suitable motion sensing technology to detect motion of the communication device 600 in three-dimensional space. The orientation sensor 620 can utilize orientation sensing technology such as a magnetometer to detect the orientation of the communication device 600 (north, south, west, and east, as well as combined orientations in degrees, minutes, or other suitable orientation metrics).

The communication device 600 can use the transceiver 602 to also determine a proximity to a cellular, Wi-Fi, Bluetooth®, or other wireless access points by sensing techniques such as utilizing a received signal strength indicator (RSSI) and/or signal time of arrival (TOA) or time of flight (TOF) measurements. The controller 606 can utilize computing technologies such as a microprocessor, a digital signal processor (DSP), programmable gate arrays, application specific integrated circuits, and/or a video processor with associated storage memory such as Flash, ROM, RAM, SRAM, DRAM or other storage technologies for executing computer instructions, controlling, and processing data supplied by the aforementioned components of the communication device 600.

Other components not shown in FIG. 6 can be used in one or more embodiments of the subject disclosure. For instance, the communication device 600 can include a slot for adding or removing an identity module such as a Subscriber Identity Module (SIM) card or Universal Integrated Circuit Card (UICC). SIM or UICC cards can be used for identifying subscriber services, executing programs, storing subscriber data, and so on.

The terms “first,” “second,” “third,” and so forth, as used in the claims, unless otherwise clear by context, is for clarity only and does not otherwise indicate or imply any order in time. For instance, “a first determination,” “a second determination,” and “a third determination,” does not indicate or imply that the first determination is to be made before the second determination, or vice versa, etc.

In the subject specification, terms such as “store,” “storage,” “data store,” data storage,” “database,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components described herein can be either volatile memory or nonvolatile memory, or can comprise both volatile and nonvolatile memory, by way of illustration, and not limitation, volatile memory, non-volatile memory, disk storage, and memory storage. Further, nonvolatile memory can be included in read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can comprise random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM). Additionally, the disclosed memory components of systems or methods herein are intended to comprise, without being limited to comprising, these and any other suitable types of memory.

Moreover, it will be noted that the disclosed subject matter can be practiced with other computer system configurations, comprising single-processor or multiprocessor computer systems, mini-computing devices, mainframe computers, as well as personal computers, hand-held computing devices (e.g., PDA, phone, smartphone, watch, tablet computers, netbook computers, etc.), microprocessor-based or programmable consumer or industrial electronics, and the like. The illustrated aspects can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network; however, some if not all aspects of the subject disclosure can be practiced on stand-alone computers. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

In one or more embodiments, information regarding use of services can be generated including services being accessed, media consumption history, user preferences, and so forth. This information can be obtained by various methods including user input, detecting types of communications (e.g., video content vs. audio content), analysis of content streams, sampling, and so forth. The generating, obtaining and/or monitoring of this information can be responsive to an authorization provided by the user. In one or more embodiments, an analysis of data can be subject to authorization from user(s) associated with the data, such as an opt-in, an opt-out, acknowledgement requirements, notifications, selective authorization based on types of data, and so forth.

Some of the embodiments described herein can also employ artificial intelligence (AI) to facilitate automating one or more features described herein. The embodiments (e.g., in connection with automatically identifying acquired cell sites that provide a maximum value/benefit after addition to an existing communications network) can employ various AI-based schemes for conducting various embodiments thereof. Moreover, the classifier can be employed to determine a ranking or priority of each cell site of the acquired network. A classifier is a function that maps an input attribute vector, x=(x₁, x₂, x₃, x₄ . . . x_(n)), to a confidence that the input belongs to a class, that is, f(x)=confidence (class). Such classification can employ a probabilistic and/or statistical-based analysis (e.g., factoring into the analysis utilities and costs) to determine or infer an action that a user desires to be automatically performed. A support vector machine (SVM) is an example of a classifier that can be employed. The SVM operates by finding a hypersurface in the space of possible inputs, which the hypersurface attempts to split the triggering criteria from the non-triggering events. Intuitively, this makes the classification correct for testing data that is near, but not identical to training data. Other directed and undirected model classification approaches comprise, e.g., naïve Bayes, Bayesian networks, decision trees, neural networks, fuzzy logic models, and probabilistic classification models providing different patterns of independence can be employed. Classification as used herein also is inclusive of statistical regression that is utilized to develop models of priority.

As will be readily appreciated, one or more of the embodiments can employ classifiers that are explicitly trained (e.g., via a generic training data) as well as implicitly trained (e.g., via observing UE behavior, operator preferences, historical information, receiving extrinsic information). For example, SVMs can be configured via a learning or training phase within a classifier constructor and feature selection module. Thus, the classifier(s) can be used to automatically learn and perform a number of functions, including but not limited to determining according to predetermined criteria which of the acquired cell sites will benefit a maximum number of subscribers and/or which of the acquired cell sites will add minimum value to the existing communications network coverage, etc.

As used in some contexts in this application, in some embodiments, the terms “component,” “system” and the like are intended to refer to, or comprise, a computer-related entity or an entity related to an operational apparatus with one or more specific functionalities, wherein the entity can be either hardware, a combination of hardware and software, software, or software in execution. As an example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, computer-executable instructions, a program, and/or a computer. By way of illustration and not limitation, both an application running on a server and the server can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems via the signal). As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, which is operated by a software or firmware application executed by a processor, wherein the processor can be internal or external to the apparatus and executes at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts, the electronic components can comprise a processor therein to execute software or firmware that confers at least in part the functionality of the electronic components. While various components have been illustrated as separate components, it will be appreciated that multiple components can be implemented as a single component, or a single component can be implemented as multiple components, without departing from example embodiments.

Further, the various embodiments can be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware or any combination thereof to control a computer to implement the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device or computer-readable storage/communications media. For example, computer readable storage media can include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips), optical disks (e.g., compact disk (CD), digital versatile disk (DVD)), smart cards, and flash memory devices (e.g., card, stick, key drive). Of course, those skilled in the art will recognize many modifications can be made to this configuration without departing from the scope or spirit of the various embodiments.

In addition, the words “example” and “exemplary” are used herein to mean serving as an instance or illustration. Any embodiment or design described herein as “example” or “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word example or exemplary is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.

Moreover, terms such as “user equipment,” “mobile station,” “mobile,” subscriber station,” “access terminal,” “terminal,” “handset,” “mobile device” (and/or terms representing similar terminology) can refer to a wireless device utilized by a subscriber or user of a wireless communication service to receive or convey data, control, voice, video, sound, gaming or substantially any data-stream or signaling-stream. The foregoing terms are utilized interchangeably herein and with reference to the related drawings.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer” and the like are employed interchangeably throughout, unless context warrants particular distinctions among the terms. It should be appreciated that such terms can refer to human entities or automated components supported through artificial intelligence (e.g., a capacity to make inference based, at least, on complex mathematical formalisms), which can provide simulated vision, sound recognition and so forth.

As employed herein, the term “processor” can refer to substantially any computing processing unit or device comprising, but not limited to comprising, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology; parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor can refer to an integrated circuit, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic controller (PLC), a complex programmable logic device (CPLD), a discrete gate or transistor logic, discrete hardware components or any combination thereof designed to perform the functions described herein. Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, to optimize space usage or enhance performance of user equipment. A processor can also be implemented as a combination of computing processing units.

As used herein, terms such as “data storage,” data storage,” “database,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components or computer-readable storage media, described herein can be either volatile memory or nonvolatile memory or can include both volatile and nonvolatile memory.

What has been described above includes mere examples of various embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing these examples, but one of ordinary skill in the art can recognize that many further combinations and permutations of the present embodiments are possible. Accordingly, the embodiments disclosed and/or claimed herein are intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.

In addition, a flow diagram may include a “start” and/or “continue” indication. The “start” and “continue” indications reflect that the steps presented can optionally be incorporated in or otherwise used in conjunction with other routines. In this context, “start” indicates the beginning of the first step presented and may be preceded by other activities not specifically shown. Further, the “continue” indication reflects that the steps presented may be performed multiple times and/or may be succeeded by other activities not specifically shown. Further, while a flow diagram indicates a particular ordering of steps, other orderings are likewise possible provided that the principles of causality are maintained.

As may also be used herein, the term(s) “operably coupled to,” “coupled to,” and/or “coupling” includes direct coupling between items and/or indirect coupling between items via one or more intervening items. Such items and intervening items include, but are not limited to, junctions, communication paths, components, circuit elements, circuits, functional blocks, and/or devices. As an example of indirect coupling, a signal conveyed from a first item to a second item may be modified by one or more intervening items by modifying the form, nature or format of information in a signal, while one or more elements of the information in the signal are nevertheless conveyed in a manner than can be recognized by the second item. In a further example of indirect coupling, an action in a first item can cause a reaction on the second item, as a result of actions and/or reactions in one or more intervening items.

Although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement which achieves the same or similar purpose may be substituted for the embodiments described or shown by the subject disclosure. The subject disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, can be used in the subject disclosure. For instance, one or more features from one or more embodiments can be combined with one or more features of one or more other embodiments. In one or more embodiments, features that are positively recited can also be negatively recited and excluded from the embodiment with or without replacement by another structural and/or functional feature. The steps or functions described with respect to the embodiments of the subject disclosure can be performed in any order. The steps or functions described with respect to the embodiments of the subject disclosure can be performed alone or in combination with other steps or functions of the subject disclosure, as well as from other embodiments or from other steps that have not been described in the subject disclosure. Further, more than or less than all of the features described with respect to an embodiment can also be utilized. 

What is claimed is:
 1. A system comprising: a distributed unit (DU) configured to generate sounding reference signal (SRS)-based beams; and a remote unit (RU) communicatively coupled with the DU over a fronthaul, wherein the RU is configured to generate demodulation reference signal (DMRS)-based beams and perform digital beamforming for an uplink using the DMRS-based beams in combination with the SRS-based beams.
 2. The system of claim 1, wherein the system comprises a split radio access network (RAN) deployment.
 3. The system of claim 1, wherein the RU comprises a massive multiple-input-multiple-output (MIMO) antenna array.
 4. The system of claim 1, wherein the digital beamforming involves matrix multiplication, and wherein a matrix for the digital beamforming includes SRS-based beam weights concatenated with DMRS-based beam weights.
 5. The system of claim 1, further comprising a radio access network (RAN) intelligent controller (RIC).
 6. The system of claim 5, wherein the RIC is configured to employ one or more artificial intelligence (AI) algorithms to analyze a performance of the uplink and determine allocation of beam generation responsibilities between the DU and the RU based on the performance.
 7. The system of claim 6, wherein the one or more AI algorithms are further configured to determine the allocation of beam generation responsibilities according to user priority, user reliability or latency requirements, user service level agreements, user channel conditions, user mobility, content type, a load on the fronthaul, a load on the DU, a load on the RU, network resource usage patterns, instantaneous user loading, or a combination thereof.
 8. The system of claim 1, wherein the DU is further configured to obtain SRS data from the RU over the fronthaul and derive SRS channel estimates using the SRS data, and wherein the DU is configured to generate the SRS-based beams using the SRS channel estimates.
 9. The system of claim 1, wherein the RU is further configured to obtain DMRS data from received signals in the uplink and derive DMRS channel estimates using the DMRS data, and wherein the RU is configured to generate the DMRS-based beams using the DMRS channel estimates.
 10. The system of claim 1, wherein the fronthaul is split in accordance with one or more open-RAN (O-RAN) standards.
 11. A method comprising: generating first beam weights by a first processor of a distributed unit (DU) in a network; transmitting, by the first processor, the first beam weights to a remote unit (RU) of the network, wherein the DU and the RU are communicatively coupled to one another via a split fronthaul; generating second beam weights by a second processor of the RU; and performing digital beamforming for an uplink of the network based on the first beam weights and the second beam weights.
 12. The method of claim 11, wherein the generating the first beam weights is based on sounding reference signal (SRS) data.
 13. The method of claim 11, wherein the generating the second beam weights is based on demodulation reference signal (DMRS) data.
 14. The method of claim 11, wherein the network comprises a radio access network (RAN) intelligent controller (RIC).
 15. The method of claim 14, further comprising, determining, by the first processor of the DU or by the RIC, a performance of the uplink, and allocating beam generation tasks between the DU and the RU based on the performance.
 16. A device, comprising: a processing system including a processor; and a memory that stores executable instructions that, when executed by the processing system, facilitate performance of operations, the operations comprising: obtaining sounding reference signal (SRS) data from a user equipment (UE) in an uplink; providing the SRS data to a centralized control unit over a fronthaul shared by the device and the centralized control unit; receiving a command from the centralized control unit to utilize demodulation reference signal (DMRS)-based beams in digital beamforming for the UE; generating one or more DMRS-based beams based on the command; and performing the digital beamforming using the one or more DMRS-based beams.
 17. The device of claim 16, wherein the command indicates that all beams for the UE are to be DMRS-based, and wherein the digital beamforming is performed using only the DMRS-based beams.
 18. The device of claim 16, wherein the operations further comprise receiving one or more SRS-based beams from the centralized control unit over the fronthaul, wherein the command indicates that digital beamforming for the UE is to be performed using both SRS-based beams and DMRS-based beams, and wherein the digital beamforming is performed using the one or more SRS-based beams and the one or more DMRS-based beams.
 19. The device of claim 16, further comprising a massive multiple-input-multiple-output (MIMO) antenna array.
 20. The device of claim 16, wherein the digital beamforming involves matrix multiplication. 